Skip to content

Conversation

@JinZhou5042
Copy link
Member

Proposed Changes

For now, whenever a recovery task is submitted, a message is printed to the user's terminal, which can be distracting.

Users don't need to know about individual recovery tasks or their operations, instead, they only care about the overall progress. If we do want to inform them, only the total number of recovery tasks is relavant

Therefore, we should stop printing Submitted recovery task xxx to their terminal. Instead, the manager should track the number of recovery tasks submitted, and expose an API for the upper-level graph executor to decide whether or not to display that information.

Merge Checklist

The following items must be completed before PRs can be merged.
Check these off to verify you have completed all steps.

  • make test Run local tests prior to pushing.
  • make format Format source code to comply with lint policies. Note that some lint errors can only be resolved manually (e.g., Python)
  • make lint Run lint on source code prior to pushing.
  • Manual Update: Update the manual to reflect user-visible changes.
  • Type Labels: Select a github label for the type: bugfix, enhancement, etc.
  • Product Labels: Select a github label for the product: TaskVine, Makeflow, etc.
  • PR RTM: Mark your PR as ready to merge.

@JinZhou5042 JinZhou5042 self-assigned this Nov 3, 2025
Copy link
Member

@dthain dthain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking that we shouldn't introduce a new API entry point for every little statistic that we would like to return. How about modifying vine_stats instead?

In the past, I would be every loath to break ABI by changing the structure size, but I think everyone is coming through Python now, and it's easier to ensure a match between Python and C.

@JinZhou5042
Copy link
Member Author

That is a good point!

@JinZhou5042 JinZhou5042 requested a review from dthain November 5, 2025 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants